The HPE 3PAR OS WSAPI process must be configured to use approved encryption and communications protocols to protect the confidentiality of remote access sessions.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-255295	HP3P-33-121100	SV-255295r877398_rule		High

Description
Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of a mechanism is selected based on the security categorization of the information. The WSAPI provides an, optional, REST interface for programmatic monitoring and control of the array operations and configuration. These configuration settings confine the server to using only TLS1.2. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000096-GPOS-00050, SRG-OS-000112-GPOS-00057, SRG-OS-000074-GPOS-00042

Description

Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of a mechanism is selected based on the security categorization of the information. The WSAPI provides an, optional, REST interface for programmatic monitoring and control of the array operations and configuration. These configuration settings confine the server to using only TLS1.2. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000096-GPOS-00050, SRG-OS-000112-GPOS-00057, SRG-OS-000074-GPOS-00042

STIG	Date
HPE 3PAR StoreServ 3.3.x Security Technical Implementation Guide	2023-11-30

Details

Check Text ( C-58968r870202_chk )
If the mission does not require WSAPI functionality, this requirement is not applicable. Verify if WSAPI is configured to run. Use the command: cli% showwsapi -d If "Service State" shows "Disabled", this is not applicable. If "HTTP State" shows "Enabled", this is a finding. If "HTTPS State" shows "Disabled", this is a finding. If "Policy" contains "no_tls_strict", this is a finding.

Fix Text (F-58912r870203_fix)
Verify if WSAPI is configured to run. Use the command: cli% showwsapi -d If "Service State" shows "Disabled", this is not applicable. Temporarily stop the WSAPI server with the command: cli% stopwsapi -f To disable the HTTP listener, and enable the HTTPS listener, use the command: cli% setwsapi -http disable -https enable To set the TLS policy to TLSv1.2 only, use the command: cli% setwsapi -pol tls_strict Restart the server with the following command: cli% startwsapi

Fix Text (F-58912r870203_fix)

Verify if WSAPI is configured to run. Use the command:
cli% showwsapi -d

If "Service State" shows "Disabled", this is not applicable.

Temporarily stop the WSAPI server with the command:
cli% stopwsapi -f

To disable the HTTP listener, and enable the HTTPS listener, use the command:
cli% setwsapi -http disable -https enable

To set the TLS policy to TLSv1.2 only, use the command:
cli% setwsapi -pol tls_strict

Restart the server with the following command:
cli% startwsapi